Method and system for associating text and segments within multi-tagged literature by application of metadata

ABSTRACT

A method and system are presented whereby the metadata describing segments of digitized text and the descriptors thereof may be inserted into the digitized text and edited by a human editor. The metadata may optionally describe the relationships between human-generated segments of a source text and the tags used to describe aspects of the segments, wherein the tags may describe narrative themes, places, characters, etc., and/or the relationships between the segments of text, the tags describing the segments of text, and data structures used to compare relationships between the tags on various segments of text (“nodes”). When the text segments, the narrative tags and/or the nodes are edited, the associated metadata is adjusted accordingly.

CO-PENDING PATENT APPLICATION

This Nonprovisional Patent Application is a Continuation-in-Part Application to Nonprovisional patent application Ser. No. 13/725,977 as filed on Dec. 21, 2012 by Inventor Lisa Quintana and titled METHOD AND SYSTEM FOR DELINEATING AND ACCESSING MULTI-TAGGED LITERATURE.

FIELD OF THE INVENTION

The present invention relates to the generation, parsing, modification, structure and structuring of electronically stored digitized text. More particularly, the present invention relates to digitized textual documents and methods and devices for organizing, rendering and experiencing segments within a digitized text, of either a newly generated or a previously authored document, and the methods by which the metadata describing the documents and organization thereof may be described.

BACKGROUND OF THE INVENTION

The market for and supply channels of digitized copies of textual documents, or “ebooks”, is presently well established in both domestic and international channels of commerce. Yet the prior art merely offers essential access to each ebook by presenting a single narrative line in simulation of the typical method of reading a hard copy text from front page to last page. While prior art ebook readers do allow a reader to (a.) record electronic bookmarks within an ebook, (b.) peruse an ebook on the basis of page number or key word selection, (c.) jump from page to page, and (d.) activate hyperlinks to move from one point to another point within an ebook, the prior art wholly fails to optimize the possibilities of offering two or more alternate narrative threads through a same ebook, and to provide efficient means by which the narrative threads and segments of the narrative may be organized by means of metadata tags.

There is therefore a long felt need to provide a method and device to establish two or more threads of separately associated segments which a reader may selectively follow while accessing an ebook.

SUMMARY OF THE INVENTION

Toward this and other objects that are made obvious in light of the disclosure, a method and system are provided for separating a digitized textual document into a plurality of textual segments, wherein each textual segment (hereinafter, “segments”) may be associated with one or more unique tags. One or more pluralities of segments may be associated with unique tags, wherein a first plurality of segments may be defined by associating each segment of the first plurality of segments with a first tag, and additional pluralities of segments are each defined by associating each segment of the particular plurality of segments with a unique and distinguishable tag. For example, a subset of segments of a source document may be selected out and each associated with a particular character. This exemplary subset of segments may, in an exemplary but not limited method, be associated with a common tag that represents an association with this particular character.

Additionally and optionally the segments may be further assigned sequence numbers that order each segment along a one-dimensional order wherein no two sequence numbers are equal, i.e., in a comparison of any two sequence numbers one sequence number will indicate an earlier relative position of the associated segment within the sequence of segments and the other sequence number of the other segment will indicate a later relative position within the sequence of segments.

Segments may be associated with tags that include various literary qualities and aspects, such as, but not limited to, one or more characters, narrators, points of view, scenes, moments in time, locales, themes, object, and/or other suitable literary aspects or qualities.

It is understood that the digitized textual document may be a digitized representation of a previously written text, e.g., “Ulysses” by James Joyce, or may be a newly authored work that is separated into segments and organized with two or more distinguishable pluralities of uniquely and differently tagged segments.

Two or more segments may include references to scenes and time line moments, wherein two or more segments may be associated with a same scene at a same time line moments, but might also each be disparately associated with different aspects of the source text, such as point of view, character or theme. Alternately or additionally, two or more segments may be associated with two or more different aspects of the source text.

When the segments are stored as segments records and tags are associated with at least two or more segments records, one or more software nodes may be instantiated at run time and/or stored within node records in electronic memory. Nodes are data structures that are associated with at least one segment record and are applied, among other uses, to determine when two segments are associated with a same tag. For example, when two segments are each separately associated with a different character but are also tagged as being related to a same scene in a plot timeline, a node may be generated that comprises references to the scene, to both characters, and to the two segments.

According to a second aspect of the method of the present invention (hereinafter, the “invented method”), an editing system comprising an editor software is provided that enables a human editor to define and populate segment records and separate a textual document into segments having different tags or different combinations of tags.

According to a third aspect of the invented method, an ebook rendering device (hereinafter, the “ebook device”) comprising a reader software is provided that enables a human reader to select a thread of segments wherein each segment of a selected thread is associated with a same tag. The ebook device may be directed by the human reader to (a.) sequentially render each segment of a selected thread; (b.) selectively render two or more segments associated with a same node; (c.) select which tag from a plurality of tags to follow in order to sequentially render segments in accordance with a predefined thread of segments; and/or (d.) enable a human reader to select or input an aspect of the textual document to apply to the pluralities of segments and select a plurality of segments on the criterion of association with the selected or input aspect of the digitized document. The selected or input aspect of the digitized document might be a character, a setting, a reference to a point within a timeline, a theme, a locale, a dialogue, and/or or a literary quality.

According to a fourth aspect of the invented method, one or more segments might be associated with more than one tag, and some or all of the text of a segment might also be comprised within an additional segment or segment record.

According to a fifth aspect of the invented method, a software structure is established wherein a plurality of nodes are interrelated and each segment is associated with at least one node. The nodes may be generated in a compilation or execution performed in light of the associations of the segments and may optionally or alternately generated at a runtime of a software program.

Optionally or additionally one or more nodes may be linked to or associated with two or more associated segments. For example, a node may enable a fictional same scene in a novel to be explicated from both (a.) a first point of view of a narrator, and (b.) a second point of view of a character who is portrayed as being present within the same scene. The invented ebook reader device may optionally enable the human reader to access two or more segments that are with a same node wherein these segments may be further associated with different tags, e.g., character tags. For example, the human reader may enjoy perusing the different points of view of different characters related to a same scene and within the general plot line or narrative of the source digitized textual document.

According to a fifth optional aspect of the invented method, a non-transitory computer-readable medium is provided that enables the ebook device to render segments in accordance with one or more aspects of the invented method.

Additionally, a method is provided by which the source text may be entered into the memory of the editing system, generating a plurality of segments from the source text. The segments of the source text may be associated by a human editor with at least one of a plurality of navigation tags and at least one of a plurality of the nodes. Additionally metadata is generated, wherein the metadata identifies the segments and at least one of the associated tag and/or at least one node. Metadata, as understood in the art, is a form of data that acts as a descriptor for other forms of data, allowing for easier perusal of data by editing systems. The metadata indicating connections between segments and tags and/or nodes may be input or edited by a human editor, and may be adjusted based upon adjustments to the segments and/or the tags and/or the nodes.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a process chart of a first invented method of generating an outline of a multi-tagged ebook;

FIG. 2 is a process chart of a first invented method of preparing a multi-tagged ebook for publication;

FIG. 3 is a is a process chart of a first preferred embodiment of a user experience in reading the invented ebook of FIG. 2;

FIG. 4 is a representation of a digitized text of FIG. 1 divided into segments;

FIG. 5 is a schematic diagram of an exemplary first segment record in which a first segment of FIG. 3 of the invented ebook is comprised;

FIG. 6 is a schematic of node diagram that is organized in accordance with the invented ebook of FIGS. 1, 2 and 3 and a plurality of segment records of FIG. 4;

FIG. 7 is a schematic diagram of an exemplary first segment record by which a first node FIG. 5 of the invented ebook is defined;

FIG. 8A is a block diagram of a first alternate embodiment of a segment record of FIG. 4 and FIG. 5;

FIG. 8B is a block diagram of a second alternate embodiment of a segment record of FIG. 4 and FIG. 5;

FIG. 8C is a block diagram of a third alternate embodiment of a segment record of FIG. 4 and FIG. 5;

FIG. 8D is a block diagram of a fourth alternate embodiment of a segment record of FIG. 4 and FIG. 5;

FIG. 8E is a block diagram of a fifth alternate embodiment of a segment record of FIG. 4 and FIG. 5;

FIG. 8F is a block diagram of a sixth alternate embodiment of a segment record of FIG. 4 and FIG. 5;

FIG. 8G is a block diagram of a seventh alternate embodiment of a segment record of FIG. 4 and FIG. 5;

FIG. 8H is a block diagram of an eighth alternate embodiment of a segment record of FIG. 4 and FIG. 5;

FIG. 8I is a block diagram of a ninth alternate embodiment of a segment record of FIG. 4 and FIG. 5;

FIG. 8J is a block diagram of a tenth alternate embodiment of a segment record of FIG. 4 and FIG. 5;

FIG. 8K is a block diagram of an eleventh alternate embodiment of a segment record of FIG. 4 and FIG. 5;

FIG. 8L is a block diagram of a twelfth alternate embodiment of a segment record of FIG. 4 and FIG. 5;

FIG. 9 is an exemplary node diagram, wherein each nodes references at least one segment record of FIG. 8;

FIG. 10 is a flow chart of an ebook reader in providing a user-interactive process that enables a human reader to access the invented ebook of FIG. 2;

FIG. 11 is a flowchart an invented method of applying a default tag for execution by the ebook reader in interaction with the reader;

FIG. 12 is a flowchart of an invented method of applying a user selected tag as executable by the ebook reader in interaction with the reader;

FIG. 13 is a flowchart of a additional aspects of the invented method of applying a user selected tag for execution by the ebook reader in interaction with the reader;

FIG. 14 is a flowchart of a fourth aspect of the invented method of applying a user selected tag as executable by the ebook reader in interaction with the reader;

FIG. 15 is an illustration of an ebook reader user interface;

FIG. 16 is an illustration of a second ebook reader interface;

FIG. 17 is a representation of a software table that associates tags of FIG. 5 with labels of FIG. 15 and FIG. 16 in one-to-one relationships;

FIG. 18 is a software flowchart of additional optional aspects of the system software of the ebook reader of FIG. 3 and FIG. 20;

FIG. 19 is a schematic diagram of an ebook editing system of FIG. 1 and publishing system of FIG. 2;

FIG. 20 is a schematic diagram of an ebook reader;

FIG. 21A is a process chart of a preferred embodiment of the invented method wherein metadata is updated in response to creation of and modifications to segment records and/or node records;

FIG. 21B is a process chart of an alternate preferred embodiment of the invented method wherein segment records and/or node records are created and/or updated based upon modifications to the metadata;

FIG. 22A is a process chart of a further preferred embodiment of the invented method wherein a segment record is populated by a human editor, and metadata is revised by a human editor;

FIG. 22B is a process chart of a yet further preferred embodiment of the invented method wherein metadata is edited, and a new segment record is populated by a human editor;

FIG. 22C is a process chart of a yet additional preferred embodiment of the invented method wherein a new segment record is populated by a human editor, and the metadata is revised by the editing system;

FIG. 22D is a process chart of a yet additional preferred embodiment of the invented method wherein metadata is revised by a human editor, and a new segment record is populated by the editing system;

FIG. 22E is a process chart of an additional preferred embodiment of the invented method wherein a new segment record is populated by the editing system and the metadata is updated by a human editor;

FIG. 22F is a process chart of a further preferred embodiment of the invented method wherein metadata is revised by the editing system and a new segment record is populated by the human editor;

FIG. 23A is a process chart of a further preferred embodiment of the invented method wherein a node record is populated by a human editor, and metadata is revised by a human editor;

FIG. 23B is a process chart of a yet further preferred embodiment of the invented method wherein metadata is modified by a human editor, and a new node record is subsequently populated by a human editor;

FIG. 23C is a process chart of a yet additional preferred embodiment of the invented method wherein a new node record is populated by a human editor, and the metadata is revised by the editing system;

FIG. 23D is a process chart of a yet additional preferred embodiment of the invented method wherein metadata is revised by a human editor, and a new node record is populated by the editing system;

FIG. 23E is a process chart of an additional preferred embodiment of the invented method wherein a new node record is populated by the editing system and the metadata is revised by a human editor;

FIG. 23F is a process chart of a further preferred embodiment of the invented method wherein metadata is revised by the editing system and a new node record is populated by the human editor;

FIG. 24A is a process chart of a further preferred embodiment of the invented method wherein a segment record is revised by a human editor, and metadata is revised by a human editor;

FIG. 24B is a process chart of a yet further preferred embodiment of the invented method wherein metadata is modified by a human editor, and a segment record is subsequently revised by a human editor;

FIG. 24C is a process chart of a yet additional preferred embodiment of the invented method wherein a segment record is modified by a human editor, and the metadata is revised by the editing system;

FIG. 24D is a process chart of a yet additional preferred embodiment of the invented method wherein metadata is revised by a human editor, and a segment record is revised by the editing system;

FIG. 24E is a process chart of an additional preferred embodiment of the invented method wherein a segment record is modified by the editing system and the metadata is revised by a human editor;

FIG. 24F is a process chart of a further preferred embodiment of the invented method wherein metadata is revised by the editing system and a segment record is modified by the human editor;

FIG. 25A is a process chart of a further preferred embodiment of the invented method wherein a node record is revised by a human editor, and metadata is revised by a human editor;

FIG. 25B is a process chart of a yet further preferred embodiment of the invented method wherein metadata is modified by a human editor, and a node record is subsequently revised by a human editor;

FIG. 25C is a process chart of a yet additional preferred embodiment of the invented method wherein a node record is modified by a human editor, and the metadata is revised by the editing system;

FIG. 25D is a process chart of a yet additional preferred embodiment of the invented method wherein metadata is revised by a human editor, and a node record is revised by the editing system;

FIG. 25E is a process chart of an additional preferred embodiment of the invented method wherein a node record is modified by the editing system and the metadata is revised by a human editor;

FIG. 25F is a process chart of a further preferred embodiment of the invented method wherein metadata is revised by the editing system and a node record is modified by the human editor;

FIG. 26 is a block diagram of the ebook, including a plurality of segment records, and metadata;

FIG. 27A is a block diagram of exemplary metadata;

FIG. 27B is a block diagram is exemplary revised metadata; and

FIGS. 28A-28D are block diagrams of exemplary node records.

DESCRIPTION

It is to be understood that this invention is not limited to particular aspects of the present invention described, as such may, of course, vary. It is also to be understood that the terminology used herein is for the purpose of describing particular aspects only, and is not intended to be limiting, since the scope of the present invention will be limited only by the appended claims.

Methods recited herein may be carried out in any order of the recited events which is logically possible, as well as the recited order of events.

Where a range of values is provided herein, it is understood that each intervening value, to the tenth of the unit of the lower limit unless the context clearly dictates otherwise, between the upper and lower limit of that range and any other stated or intervening value in that stated range, is encompassed within the invention. The upper and lower limits of these smaller ranges may independently be included in the smaller ranges and are also encompassed within the invention, subject to any specifically excluded limit in the stated range. Where the stated range includes one or both of the limits ranges excluding either or both of those included limits are also included in the invention.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Although any methods and materials similar or equivalent to those described herein can also be used in the practice or testing of the present invention, the methods and materials are now described.

It must be noted that as used herein and in the appended claims, the singular forms “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise. It is further noted that the claims may be drafted to exclude any optional element. As such, this statement is intended to serve as antecedent basis for use of such exclusive terminology as “solely,” “only” and the like in connection with the recitation of claim elements, or use of a “negative” limitation.

Referring now generally to the Figures and particularly to FIG. 1, FIG. 1 is a process chart of a first invented method of generating a multi-tagged ebook 2 that may be rendered by an invented ebook 4. In step 1002 either an existing text is digitized or digitized text is generated and selected as a digitized source text 100 (hereinafter, “source text” 100). The source text 100 of step 1002 is then input into an editing system 200 by direct keyboard input, or by download from an electronics communications network, e.g., the Internet, or by upload from a computer medium, e.g., a digital memory stick or a digital memory disc. A human editor (hereinafter, “editor”) applies the editing system 200 in step 1006 to generate a plurality of digitized textual segments SG.001-SG.N (hereinafter, “segments” SG.001-SG.N) selected from the source text 100. It is understood that elements of the source text 100 may be duplicated in more than one derivative segment SG.001-SG.N. In response to interaction with the editor, the editing system 200 forms separate segment records SR.01-SR.N in step 1008, wherein each segment record SR.01-SR.N preferably contains at least one segment SG.001-SG.N. The editor assigns one or more tags T.01-T.N & T.DEF to one or more segment records SR.01-SR.N in step 1010. The editor preferably, but optionally, alternatively or additionally, assign a unique sequence number SEQ.001 to SEQ.N to each segment record SR.01-SR.N, whereby each segment record SR.01-SR.N has a unique segment number SEQ.001-SEQ.N that orders the segments according to a one-dimensional sequence wherein no two segment records SR.01-SR.N have the same sequence number SEQ.001-SEQ.N and each sequence number SEQ.001-SEQ.N relates a specific and unique position within the one-dimensional hierarchical structure of the one-dimensional sequence.

The significance and utility of the invented method of the tags T.01-T.N and the segment records SR.01-SR.N will be further explicated in the present disclosure. Examples of aspects of the source text 100 that may be indicated by tags are scene, moment within a time line, character point of view, narrative thread, theme, alternate plot line, alternate time line and/or other suitable literary quality known in the art.

It is understood that the steps of 1006 through 110 may be accomplished as repeated loops, or as iterative loops, as may also be the case of steps 1002 through 1012.

A pre-publication, formatted ebook outline 500 is thereupon generated in step 1012, wherein the ebook outline 500 includes all of the segments SG.001-SG.N and segment records SR.01-SR.N generated in one or more execution of the steps of 1002 through 1012, wherein one or more segment records SR.01-SR.N may be revised or deleted in this prepublication process. It is understood that the steps of 1006 through 110 may be accomplished as repeated loops, or as iterative loops, as may also be the case of steps 1002 through 1012. It is further understood that graphics and additional digitized textual data may be linked with or added to the ebook outline 500 or one or more segment records SR.01-SR.N in one or more executions of step 1008.

Referring now to FIG. 2, FIG. 2 is a process chart of a publication process. The ebook outline 500 is received by a publishing system 600 in step 2002. A font range is assigned to the ebook outline 500 in step 2004 and a table of contents is formed and added to the ebook outline 500 in step 2006. Preferably, a human publisher (hereinafter, “publisher”) selects and links skin art to the ebook outline 500 in step 2008 and frontispiece statements, e.g., copyright, publisher identification and address, ISBN and publication data, is added to the ebook outline 500 in step 2010. Customized and/or standardized buttons, icons and signage are added to the ebook outline 500 in step 2012. The publisher than permanently selects, signifies and assigns integral elements of the ebook outline 500 in step 2014. The invented ebook 2 is then released in step 2016 for commercial or public distribution in step 2016 through electronic media and/or electronic communications networks, e.g., the Internet.

Referring now to FIG. 3, FIG. 3 is a process chart of a human reader's access of the invented ebook 2 by means of an ebook reader 4 having a touch display screen 5. It is understood that the ebook reader 4 may be a general purpose computer, e.g., a tablet, laptop or desktop computer, that is configured with an invented ebook reader software SW.1, or a special purpose ebook reader, such as a KINDLE™ or Nook™ ebook reader. The human reader (hereinafter, “reader”) downloads or uploads the ebook 2 into a digital memory 4A of the ebook reader 4 in step 3002 and directs the ebook reader in step 3004 to initiate visual and/or auditory rendering of the invented ebook.

It is further understood that the nodes ND.001-N.D of the ebook 2 might be recorded as node records NR.01-NR.N and stored in the ebook reader 4 and/or alternatively or optionally generated at run time by the ebook reader 4 and after receipt by the ebook reader 4 of a user selection command of the ebook 2 of step 3004.

In optional step 3006, the reader directs the ebook reader 4 to follow a tag T.01-T.N as selected by the reader in order to provide a user directed nodal pathway through the invented ebook 2. In the alternative, the ebook reader 4 will follow a default nodal pathway through the invented ebook 4 when the reader makes no tag T.01-T.N selections by selecting segments records SR.01-SR.N that each include a default tag T.DEF in an order determined by the sequence numbers SEQ.001-SEQ.N and sequentially rendering the segments SG.001-SG.N of these segment records SR.01-SR.N that include the default tag T.DEF.

In the reading process loop of step 3010 through step 3018, the reader may direct the ebook reader 4 to proceed from step 3010 to step 3012 to exit the reading process loop 3010 through 3018 and proceed on to alternate computational operations. Alternatively, the reader may instruct the ebook reader 4 to proceed to iteratively render successive segment records SR.01-SR.N as accessed in accordance with a tag selection, or default tag selection, of step 3006. In the alternative, the reader in step 3014 may select an alternate tag T.01-T.N. or an alternate segment record SR.01-SR.N associated with a current node ND.001-ND.N may be selected by the reader in step 3016, or an alternate tag T.01-T.N or alternate node ND.001-ND.N may be selected by the reader in a search process of step 3018.

Referring now to FIG. 4, the source text 100 is illustrated as including a header 102 and being divided into segment SG.104 through Nth segment SG.N, wherein N may be as large as the total count of distinguishable words or characters of the source text 100. It is noted that content of the source text 100 may be shared by, or duplicated within, one or more segments SG.104 through SG.N, as illustrated by shared content 114.

Referring now to FIG. 5, FIG. 5 is an illustration of an exemplary first segment record 302 that includes a first segment record header SRH.001, the first segment SG.104 of the source text 100, and a first segment record tail SRT.001. The first segment record header SRH.001 includes a first segment record identifier SR.ID.001, the default tag T.DEF, and one or more tags T.01-T.N associated by the editor with the first segment SG.104, and a sequence number SEQ.001 assigned by the editor. The exemplary first record 302 may optionally further include references to one or more nodes ND.001-ND.N that are associated with the first segment record 302. The optional first segment record tail SRT.001. contains data useful in managing and transmitting the first segment record SR. 001.

Referring now to FIG. 6, FIG. 6 is an entity diagram of four nodes ND.001-ND.004 of the plurality of nodes ND.001-ND.N. The plurality of nodes ND.001-ND.N are instantiated and generated upon the basis of a query generated by a user in step 3006, or alternatively by a default selection of the ebook reader software SW.1 when the reader does not select a tag T.01-T.N in step 3306 or later.

Referring now to FIG. 7, FIG. 7 is an illustration of an exemplary first node record 702 by which the first node ND.001 of FIG. 5 of the invented ebook is defined and that includes a first node record header NRH.001 and a first node record tail NRT.001. The first node record header NRH.001 includes a first node record identifier NR.ID.001, one or more segment record identifiers SR.ID, one or more tags T.01-T.N by the instant reader query of step 3006, and one or more node record identifiers NR.ID. The one or more tags T.01-T.N may alternatively provided as a default set of tags T.01-T.N by the ebook reader software SW.1.

Referring now generally to the Figures and particularly to FIGS. 8A through 8L, FIGS. 8A through 8L each present aspects of individual segment records SEG.800-SEG.822 that each contain unique (a.) sequence numbers SEQ.800-SEQ.822; (b.) segments of the source text SG.800-SG.822; and (c.) combinations of tags, a single sequence number, and a segments. A plurality of three segment records SR.800, SR.802, SR.804 and SR.806 each include a same plot line moment tag T.02 that indicates that each of the four segments SEG.800, SEG.802, SEG.804 and SEG.806 separately comprised within these four segment records SR.800, SR.802, 804 & SR.806 are tagged by the editor as occurring contemporaneously within a plot timeline. Segment records SR.800, SR.802, SR.804 and SR.806 thereby form, or are comprised within, a first plot line moment thread TH.02 as indicated in FIG. 9.

The four segment records SR.802, SR.808, SR.810 & SR.812 each comprise a first character tag T.04 that indicates that the four individual segments SEG.802, SEG.808, SEG.810 & SEG.812 separately comprised within each of these four segment records SR.802, SR.808, SR.810 & SR.812 are each associated with a same first character. These four segment records SR.802, SR.808, SR.810 & SR.812 thereby define, or may be comprised within, a first character thread TH.2 as indicated in FIG. 9.

Similarly, three narrative voice segment records SR.806, SR.814 & SR.816 each comprise a first narrative voice tag T.06 that indicates that each of the three individual segments SEG.806, SEG.814 & SEG.816 separately comprised within these three segment records SR.806, SR.814 & SR.816 are each associated with a same first narrative voice. The three narrative voice segment records SR.806, SR.814 & SR.816 thereby define, or may be comprised within, a first narrative voice thread TH.3 as indicated in FIG. 9.

The segment records SR.800-SR.822 further comprise segment record identifiers SR.ID.800-SR.ID.822, by which the segment records SR.800-SR.822 may be identified within the system and/or by the human editor.

Referring now to FIG. 9, FIG. 9 is a representation of a plurality of nodes ND.900-914 that are generated by the ebook reader 4 prior to, or at runtime, of the ebook 2 and that reference the segment records SR.800-SR.816 of FIG. 8. Nodes ND.900, ND.902 and N904 each reference at least one segment record SR.800, SR.802, SR.804 and SR.806 of the first plot line moment thread TH.02, wherein each of these four segment records SR.800, SR.802, SR.804 and SR.806 separately each include the plot line moment tag T.02. It is noted that the second node ND.902 references the two segment records SR.802 and SR.806.

Four nodes ND.902, ND.906, ND.908 and ND.910 each reference an individual segment record SR.802, SR.808, SR.810 and SR.812 that are comprised within the first character thread TH.04 and indicated by an inclusion of the first character tag T.04 in each of the first character thread segment records SR.802, SR.808, SR.810 & SR.812.

Three nodes ND.902, ND.912, and ND.914 each reference an individual segment record SR.806, SR.806, SR.814 and SR.816 that are comprised within the first narrative voice thread TH.06 and indicated by an inclusion of the first narrative voice tag T.06 in each of the first character thread segment records SR.806, SR.812 & SR.816.

It is understood that in various preferred embodiments of the method of the present invention that one or more nodes ND.001-ND.N may include more than a reference to a segment records SR.01-SR.N, and may comprise some or all of the structure and information of one or more segment records SR.01-SR.N.

FIG. 10 is a flow chart of the ebook reader 4 in providing a user-interactive process that enables the reader to access the invented ebook 2 in selectable pathways of nodes through the ebook 2. The plurality of nodes ND.001-ND.N are generated by reader interaction in step 3006 of FIG. 3, which may include the reader inputting or selecting an aspect of the ebook 2 that is associated with a tag T.001-TN, or alternatively, by a default selection by the ebook reader software SW.1 of a default tag T.DEF.

For example, where the editor wishes to associate a particular and unique third character tag T.BILL with a fictional character BILL mentioned in the invented ebook, the third character tag T.BILL will be entered by the editing system 200 as directed by the editor into selected segment records SG.001-SG.N. When the reader requests to sequentially access each segment record SG.001-SG.N that is associated with the third character tag T.BILL, the reader will input into the ebook reader 4, by icon selection or textual input, an interest in the character BILL, and the reader software will thereupon generate and associate a node ND.001-ND.N for each segment record SG.001-SG.N that contains the third character tag T.BILL.

The ebook reader 4 may further optionally associate additional segment records SG.001-SG.N with one or more nodes ND.001-ND.N when an additional record SG.001-SG.N lacks a reference to the third character tag T.BILL but includes a degree of commonality with the immediately associated segment record SG.001-SG.N. For example, when the segment record SR.818 includes both (a.) a second plot line moment tag T.T2 and (b.) a place tag T.GARDEN that relates to a notional garden setting, and the segment record 820 includes both the second plot line tag T.T2 and the place tag T.GAR but also includes a reference to a fourth character tag T.SUE that relates to a fourth character SUE, the second node ND.002 may be generated by the editing software include a reference to the segment record SR. 820 based on the commonality of the sharing the place tag T.GARDEN and the second plot line moment tag T.T2. The ebook reader software SW.1 will thereby be enabled to expeditiously respond to requests by the reader to access segments SG.001-SG.N that are tangentially related to the previously selected third character T.BILL but do not include the third character T.BILL that is optionally the rationale for the a generation of the plurality of nodes ND.001-ND.N.

Referring now generally to the Figures and particularly to FIG. 10, the ebook reader 4 is energized and boots up in step 1000, and in step 10002 determines whether to cease processing the ebook reader software SW.1 and proceed on to alternate computational operations of step 10004. When the ebook reader 4 determines to not proceed on to step 10004 from step 10002, the ebook reader 4 proceeds on to step 10006 and to determine if an ebook 2 selection command has been received from the user. When a selection command is detected by the ebook reader 4 in step 10006, the ebook reader 4 proceeds on from step 10006 to a first execution of step 10008 and to select a default first segment record SR.01 in step 10010 from which to render the default segment SG.104 unless the user inputs a segment select command that indicates selection of an identified alternate segment SG.106-SG.N or segment record SR.01-SR.N. The ebook reader 4 thereupon determines in step 10012 whether to follow a default tag T.DEF of step 10014 or a to follow a tag T.001-T.N provided or selected by the user in a tag selection command. The ebook reader then either generates the plurality of nodes N.001-ND.N that each reference or include at least one segment record SR.01-SR., and proceeds to render a segment SEG.104-SG.N in step 10018 selected from the first node ND.001-ND.N, by reference or inclusion in the instant node ND.001-ND.N. The ebook reader 4 then determines in step 10020 whether to continue sequentially rendering segments SG.001-SG.N by successive executions of the loop of steps 10008 through 10020, or to proceed repeat an execution of step 10002. The ebook reader software SW.1 provides the machine executable instructions required by the ebook reader 4, as directed by user commands, to execute steps 10002 through 10020.

Referring now generally to the Figures and particularly to FIG. 11, FIG. 11 is a flowchart of a second preferred embodiment of aspects of the invented method of applying a default tag T.DEF for execution by the ebook reader 4 in interaction with the reader. The ebook reader 4 determines whether the reader has selected an ebook 2 for rendering in step 1102, and moves on to alternate computational operations of step 1104 when the ebook reader 4 does not detect a user command to select an ebook 2 in step 1102. When the ebook reader 4 in step 1102 detects a user command to select and render an ebook 2, the ebook reader 4 proceeds on to step 1106 and initializes a segment counter CS, and determines in step 1108 whether a tag T.001-T.N has been selected or input by the user. When the ebook reader 4 determines in step 1108 that the user has input or selected a tag T.001-TN, the ebook reader 4 proceeds form step 1108 to step 1110 and to perform the process of FIG. 12.

Alternatively, when the ebook reader 4 determines in step 1108 that the user has not input or selected a tag T.001-TN, the ebook reader 4 proceeds from step 1108 to step 1112 and to proceed to sequentially render the segment records SR.01-SR.N that reference the default tag T.DEF. The ebook reader 4 proceeds from step 1112 to execute the logic of steps 1112 through 1122 until the ebook reader 4 determines in an execution of step 1116 that the segment counter CS has been incremented by successive increments to become equal to a maximum count N of segment records SR.01-SR.N, or the user directs the ebook reader 4 to cease rendering the selected ebook 2. More particularly, the ebook reader 4 sequentially examines each segment record SR.01-SR.N to determine if each segment record SR.01-SR.N references or includes the default tag T.DEF, and sequentially renders each segment record SR.01-SR.N that references or includes the default tag T.DEF in step 1120. The user prompts the ebook reader 4 to proceed on to a next segment record in step 1122.

Referring now generally to the Figures and particularly to FIG. 12, FIG. 12 is a flowchart of a third preferred embodiment of aspects of the invented method applying a user selected tag T.001-T.N as executable by the ebook reader 4 in interaction with the reader. In steps 1200 through 1214 the ebook reader 4 sequentially selects each segment record SR.01-SR.N step 1202 and sequentially renders each segment record SR.01-SR.N in step 1210 that references or includes the user selected tag T.001-T.N detected in step 1108. The user prompts the ebook reader 4 to proceed onto a succeeding segment record SR.01-SR.N in step 1214. The ebook reader 4 will continue incrementing the segment counter CS in repeated execution of steps 1202 through 1214 until either (a.) the segment counter becomes equal to or exceeds a maximum segment count N; or (b.) the user enters a command to stop rendering segments SG.001-SG.N in either step 1206 or step 1214.

Referring now generally to the Figures and particularly to FIG. 13, FIG. 13 is a flowchart of a third preferred embodiment of aspects of the invented method applying a user selected tag T.001-T.N as executable by the ebook reader 4 in interaction with the reader, whereby the reader directs the ebook reader 4 to select segments SG.001-SG.N associated with an alternate tag T.001-T.N for rendering after the reader previously having selected a first tag T.001-T.N in a previous execution of step 1108. During a rendering in step 1210 of a segment SG.001-SG.N, the user queries whether any other segment records SR.01-SR.N are associated with a same node ND.001-ND.N as the segment record SR.002-SR.N selected in the most recent execution of step 1210. If no additional associated segment records SR.01-SR.N are determined in step 1304, the ebook reader 4 proceeds on to step 1306 and reports to the user a rendered message to that effect. If at least one additional associated segment record SR.01-SR.N is determined in step 1304, the ebook reader 4 proceeds on to step 1308 and render a message indicating the additional tag(s) T.001-T.N in step 1308.

The ebook reader 4 determines in step 1310 whether the reader has selected a different tag T.001-T.N than applied in the most recent execution of step 1210. When the ebook reader 4 determines in step 1310 that the reader has selected a new tag T.001-TN, the ebook reader 4 renders the segment SG.001-SG.N of the segment record SR.01-SR.N comprising the tag T.001-T.N selected in step 1310. As directed by the reader, the ebook reader 4 ceases rendering the segment SG.001-SG.N of step 1312, and then proceeds from step 1314 to step 1206, and thereafter selects segments SG.001-SG.N for rendering that include the newly selected tag of step 1310 in further implementations of steps 1202 through 1214.

Referring now generally to the Figures and particularly to FIG. 14, FIG. 14 is a flowchart of a fourth preferred embodiment of aspects of the invented method applying a user selected tag T.001-T.N as executable by the ebook reader 4 in interaction with the reader, whereby the reader directs the ebook reader 4 to follow an alternate tag T.001-T.N after initially selecting out segment records SR.01-SR.N that include or reference the default tag T.DEF.

During a rendering in step 1120 of a segment SG.001-SG.N, the user queries whether any other segment records SR.01-SR.N are associated with a same node ND.001-ND.N as the segment record SR.002-SR.N selected in the most recent execution of step 1120. If no additional associated segment records SR.01-SR.N are determined in step 1404, the ebook reader 4 proceeds on to step 1406 and reports to the user a rendered message to that effect. If at least one additional associated segment record SR.01-SR.N is determined in step 1404, the ebook reader 4 proceeds on to step 1408 and render a message indicating the additional tag(s) T.001-T.N in step 1408.

The ebook reader 4 determines in step 1410 whether the reader has selected a different tag T.001-T.N than applied in the most recent execution of step 1120. When the ebook reader 4 determines in step 1410 that the reader has selected a new tag T.001-TN, the ebook reader 4 renders the segment SG.001-SG.N of the segment record SR.01-SR.N comprising the tag T.001-T.N selected in step 1410. As directed by the reader, the ebook reader 4 ceases rendering the segment SG.001-SG.N of step 1412, and then proceeds from step 1414 to step 1116, and thereafter selects segments SG.001-SG.N for rendering that include the newly selected tag of step 1410 in further implementations of steps 1112 through 1122.

Referring now generally to the Figures and particularly to FIG. 15, FIG. 15 is an illustration of a user interface 1500 of the ebook reader 4 as rendered on the ebook reader display screen 5 under as directed by user interaction and the ebook reader system software SW.1. In this exemplary illustration, a selected text segment SG.802 that is stored within or associated with the exemplary segment record SR.802 is rendered. The current tag T.04, as previously selected by the reader, and that the ebook reader software SW.1 is therefore currently following, is indicated by a first tab label TAB.1500. Additional tags T.02 & T.BILL comprised within or referenced by the exemplary segment record SR.802 are presented respectively by two additional tab labels TAB.1502A and TAB.1502B. In further addition, a fourth tag T.06 of an alternate segment record SR.806 that is associated with a same node ND.902 as is the currently rendered segment SG.802 is indicated by a fourth tab label TAB.1502C.

The user interface 1500 further includes command three command buttons 1504, 1506 & 1508 and a search string input and activation box 1510. The reader may direct the ebook reader 4 to proceed to render a next segment SG.810 in sequentially following the second tag T.04 by activating the NEXT command button 1506. Alternatively, the reader may direct the ebook reader 4 to proceed to render a previous segment SG.808 in following the second tag T.04 in reverse sequence by activating the PREVIOUS command button 1504. Additionally, the reader may direct the ebook reader 4 to cease to render segments SG.001-SG.N by selecting the REST/END command button 1508. Yet alternatively, the ebook reader 4 may enter a textual search string in the string input and activation box 1510 and then activate this box 1510 to direct the ebook reader software SW.1 to find and report instances of the entered string in the ebook 2.

The reader may further direct the ebook reader 4 to render an alternate segment SG.806 by selecting a nodal tab, e.g. fourth tab label TAB.1502C that represents an alternative segment SG.806 that is associated by a node ND.902 with the currently rendered segment SG.802. When an alternate segment record SR.01-SR.N is selected by the reader, the newly selected segment SG.001-SG.N of that selected record SR.01-SR.N is then rendered in the ebook display screen 5 and the current tab label TAB.1500 is revised to reference the newly accessed segment record SR.01-SR.N. For example, should the reader select the third tab label TAB.1502C when rendering the exemplary segment SG.802, the ebook reader SW.1 would react by rendering the alternate text SG.806 of segment record SR.806 and alter the first tab label TAB.1500 to reference both the alternate tag T.06 and the segment record SR.806 that comprises the newly rendered segment SG.806. The additional tab labels TAB.1502A-1502C are also then updated to reference the tab associations of the newly selected segment record SR.806. The command buttons of NEXT 1500A and PREVIOUS 1500B would then track the tag T.06 newly referenced by the first TAB.1500.

Referring now generally to the Figures and particularly to FIG. 16, FIG. 16 is an illustration of a second user interface 1600 (or “UI” 1600) of the ebook reader 4 as rendered on the ebook reader display screen 5 and generated by the ebook reader system software SW.1 in interaction of the ebook reader 4 with the user. In this exemplary illustration of FIG. 16, a selected text 1602 of an exemplary segment SG.810 that is stored within or associated with the exemplary subsequent segment record SR.810 is rendered in the ebook display screen 5. A previous button 1604 and a next button 1606 are visually rendered in the display screen 5 and enable the user to respectively select the previous segment record SR.802 or the next segment record SR.812 of the first thread TH.04 for deriving a next or following rendering of text 1602 in the display screen 5. Label buttons 1610-1622 enable the user to make choices to select alternate tags T.01-T.N and thereby follow alternate threads TH.1-TH.3 and TH.5-TH.N or to continue to follow a selected thread TH.1-TH.N and render text 1602 and images selected from or associated with segment records SR.01-SR.N. A visually rendered home button 1624 enables the user to direct the ebook reader 4 to return to displaying a home page. An informational text 1626 informs the user about the current ebook 2 being rendered and may provide information concerning the currently rendered text 1602 in relation to the entire ebook 2. A visually rendered scroll control 1628 allows the user to direct the ebook reader 4 to render text 1602 from a single segment record SR.01-SR.N or of a currently selected thread TH.1-TH.N.

The label buttons 1608-1622 may optionally or additionally (a.) be visually shaded or affected to indicate which tag T.01-T.N is being currently followed, e.g., character label CHAR.1 1608 and location label LOC.1 1610; (b.) about other tags T.01-T.N with which the currently rendered text 1602 is associated, e.g. second character label CHAR.2 1612 and third location label LOC.3 1622; and/or additional labels 1614-1620 that are available within the ebook 2 and associated with different tags.

Referring now generally to the Figures and particularly to FIG. 17, FIG. 17 is an illustration of a tag to label table 1700 that separately associates (a.) rendered labels 1610-1622 and tabs 1500, 1504, 1506 1502A-1502C with (b.) tags T.01-T.N. Each label/tab to tag pair has a unique identifier PAIRID.1-PAIR.DEF.

It is understood that certain tags are durably associated with individual labels, for example a second location label LOC.2 is durably related to a ninth tag T.09, a sixth character label CHAR.6 is durably related to a fifth tag T.05, and a default label LABEL.DEF with the default tag T.DEFAULT in accordance with the second UI 1600. It is further understood that the ebook system software SW.1 may alternately or additionally alter the associations of tags T.01-T.N with tabs 1500-1508 in accordance with the user interface 1500.

Referring now generally to the Figures and particularly to FIG. 18, FIG. 18 is a software flowchart of additional optional aspects of the system software SW.1 of the ebook reader 4. The ebook reader 4 renders text and images 802 in step 18.02 from the most recently selected segment record SR.01-SR.N, for example the second exemplary segment SG.802 of the second exemplary segment record SR.802. In step 18.04 the ebook reader 4 determines whether a label or tab of the as rendered on the display 5 has been selected by the user. When the ebook reader 4 determines in step 18.04 that no tab or label has been selected by the user, the ebook reader 4 proceeds on step 18.06 and to determine whether to continue rendering content from the most recently selected segment record or to proceed on to step 18.08 and to perform alternate computational processes. The ebook reader 4 more proceed from step 18.06 to step 18.08 on the basis of (a.) a time out condition; (b.) a receipt of a detection of a user selection of the REST/END label 1508; or (c.) a receipt of a power down command down from the user.

When the ebook reader 4 proceeds from step 18.06 to step 18.02, the ebook reader 4 continues to render the content from most recently selected segment record SR.01-SR.N. When the ebook reader 4 determines in step 18.04 a tab or label selection by the user has been detected, the ebook reader 4 proceeds on step 18.10 and to determine whether a next segment record SR.01-SR.N of the same thread TH.01-TH.N of the segment record currently being rendered shall be rendered in a following execution of step 18.02. Alternatively, the ebook reader 4 determines in step 18.12 to determine whether a previous segment record SR.01-SR.N of the same thread TH.01-TH.N of the segment record currently being rendered shall be rendered in a following execution of step 18.02. Still alternatively, the ebook reader 4 determines in step 18.14 if the user has indicated that an segment record SR.01-N of an alternate tag T.01-T.N shall be selected for rendering. When the ebook reader 4 determines in step 18.14 that a segment record SR.01-SR.N of a tag T.01-T.N or thread TH.01-TH.N different from the selected tag T.01-T.MN or Thread TH.01_TH.N of the most recently rendered record, the ebook reader 4 references the table 1700 to relate the selected tab 1500, 1502A-1502C or label 1610-1622 to a tag T.01-T.N.

FIG. 19 is a schematic diagram of the ebook editing system 200 and/or ebook publishing system 600. The ebook editing system 200 may be or comprise (a.) a network-communications enabled THINKSTATION WORKSTATION™ notebook computer marketed by Lenovo, Inc. of Morrisville, N.C.; (b.) a NIVEUS 5200 computer workstation marketed by Penguin Computing of Fremont, Calif. and running a LINUX™ operating system or a UNIX™ operating system; (c.) a network-communications enabled personal computer configured for running WINDOWS XP™, VISTA™ or WINDOWS 7 ™ operating system marketed by Microsoft Corporation of Redmond, Wash.; (d.) a MACBOOK PRO™ personal computer as marketed by Apple, Inc. of Cupertino, Calif.; (e.) an IPAD™ tablet computer as marketed by Apple, Inc. of Cupertino, Calif.; (f.) an IPHONE™ cellular telephone as marketed by Apple, Inc. of Cupertino, Calif.; (g.) an HTC TITAN II™ cellular telephone as marketed by AT&T, Inc. of Dallas, Tex. and running a WINDOWS 7 ™ operating system as marketed by Microsoft Corporation of Redmond, Wash.; (h.) a GALAXY NEXUS™ smart phone as marketed by Samsung Group of Seoul, Republic of Korea or and running an ANDROID™; (i.) a TOUGHPAD™ tablet computer as marketed by Panasonic Corporation of Kadoma, Osaka, Japan and running an ANDROID™ operating system as marketed by Google, Inc. of Mountain View, Calif.; or (j.) other suitable computational system or electronic communications device known in the art.

The editing system 200A central processing unit is bi-directionally communicatively coupled by a communications bus 200B to a display module 200C, an input module 200D, a wireless communications interface module 200E, a system memory 200F, an optional touch screen input 200G, an optional firmware 200H and/or an optional electronic media read/write module 200I. The electronic media read/write module 200I and an electronic media 1902 are selected to enable reading and writing of the ebook 2 to and from the editing system 200. The editing system software SW.5 enables the editing system 200 to the perform the aspects of the invented method as disclosed herein in the Figures and accompanying text. The network 1900 may be or comprise the Internet, a telephony network, and/or other computer electronic communications network.

FIG. 20 is a schematic diagram of an ebook reader 4. The ebook reader 4 may be or comprise (a.) a KINDLE ebook reader as marketed by Amazon, Inc. of Seattle, Wash.; (b.) a NOOK ebook reader as marketed by Barnes & Noble, Inc. of New York, N.Y.; (c.) an IPHONE™ cellular telephone as marketed by Apple, Inc. of Cupertino; (d.) an IPAD™ tablet computer adapted for generation of digitized photographic documents and capable of bi-directional communications via the telephony network and the Internet 6 as marketed by Apple, Inc. of Cupertino, Calif.; (e.) an HTC TITAN II™ cellular telephone as marketed by AT&T, Inc. of Dallas, Tex. and running a WINDOWS 7™ operating system as marketed by Microsoft Corporation of Redmond, Wash.; (f.) a GALAXY NEXUS™ smart phone as marketed by Samsung Group of Seoul, Republic of Korea and running an ANDROID™ operating system as marketed by Google, Inc. of Mountain View, Calif.; (g.) a TOUGHPAD™ tablet computer as marketed by Panasonic Corporation of Kadoma, Osaka, Japan and running an ANDROID™ operating system as marketed by Google, Inc. of Mountain View, Calif.; or (h.) other suitable text display system known in the art.

The ebook reader central processing unit 4B is bi-directionally communicatively coupled by a reader communications bus 4B to a display module 4C and the touch screen display 5, a reader input module 4D, a reader wireless communications interface module 4E, the reader system memory 4A, an optional firmware 4F and/or an optional reader electronic media read/write module 4G. The electronic media read/write module 4G and the electronic media 1902 are optionally selected to enable reading and writing of the ebook 2 to and from the ebook reader 4. The ebook reader system software SW.1 enables the ebook reader 4 to perform the aspects of the invented method as disclosed herein in the Figures and accompanying text. A first GUI software SW.6 enables the first user interface and process of FIG. 15 and the user interaction as disclosed in the accompanying text. A second GUI software SW.7 enables the process of the second UI of FIG. 16 and the user interaction as disclosed in the accompanying text.

Referring now generally to the Figures, and particularly to FIG. 21A, FIG. 21A is a process chart of a preferred embodiment of the invented method wherein metadata MD.01-MD.N is updated in response to creation of and modifications to segment records SR.01-SR.N and/or node records NR.01-NR.N. The following steps may be executed in their entirety by a human editor, or may alternately be executed by a human editor in combination with the editing system 200 as enabled by the system software SW.5, as described in greater detail in additional drawings described below. In step 21A.02 it is determined whether new digitized textual data has been received. When it is determined that no new digitized textual data has been received, alternate operations are executed in step 21A.04. Alternately, when it is determined in step 21A.02 that new digitized textual data has been received, it is determined in step 21A.06 whether a new record is necessary to categorize the information within the new digitized textual data; the new record may optionally be a new segment record SR.NEW, or may optionally be a new node record NR.NEW. When it is determined that either a new segment record SR.NEW or a new node record NR.NEW is necessary, the new segment record SR.NEW or new node record NR.NEW is created and populated in step 21A.08. In step 21A.10 the metadata is updated to reflect the newly created and populated segment record SR.NEW or node record NR.NEW. Subsequently, alternate operations are executed in step 21A.04.

In the alternative, when it is determined in step 21A.06 that no new record is necessary to categorize the information within the new digitized textual data, in step 21A.12 it is determined whether modification to a segment record SR.01-SR.N is needed to reflect the received new digitized textual data. When it is determined that modification to a segment record SR.01-SR.N is needed to reflect the received new digitized textual data, the segment record SR.01-SR.N is modified in step 21A.14, and the metadata MD.01-MD.N is subsequently updated to reflect the modification to the segment record SR.01-SR.N in step 21A.16. Alternately, when it is determined in step 21A.14 that no modification to a segment record SR.01-SR.N is necessary in response to the received new digitized textual data, in step 21A.18 it is determined whether modifications to a node record NR.01-NR.N are necessary in response to the received new digitized textual data. When it is determined in step 21A.18 that a node record NR.01-NR.N need be modified in response to the received new digitized textual data, the node record is updated in step 21A.20. Subsequently, in step 21A.22, the metadata MD.01-MD.N is updated to reflect the modifications to the node record NR.01-NR.N. Alternate operations are subsequently executed in step 21A.04. When, in the alternative, it is determined in step 21A.18 that no modification need be made to the node record ND.01-ND.N, the steps 21A.02 through 21A.22 are executed as deemed necessary by the human editor or by the editing system 200, enabled by the system software SW.5.

Referring now generally to the Figures, and particularly to FIG. 21B, FIG. 21B is a process chart of an alternate preferred embodiment of the invented method wherein segment records SR.01-SR.N and/or node records NR.01-NR.N are created and/or updated based upon modifications to the metadata MD.01-MD.N. The following steps may be executed in their entirety by a human editor, or may alternately be executed by a human editor in combination with the editing system 200 as enabled by the system software SW.5, as described in greater detail in additional drawings described below. In step 21B.02 it is determined whether new digitized textual data has been received. When it is determined that no new digitized textual data has been received, alternate operations are executed in step 21B.04. Alternately, when it is determined in step 21B.02 that new digitized textual data has been received, it is determined in step 21B.06 whether a new record is necessary to categorize the information within the new digitized textual data; the new record may optionally be a new segment record SR.NEW, or may optionally be a new node record NR.NEW. When it is determined that either a new segment record SR.NEW or a new node record NR.NEW is necessary, metadata MD.01-MD.N is modified or generated to describe the new segment record SR.NEW or new node record NR.NEW in step 21B.08. In step 21B.10 a new segment record SR.NEW or node record NR.NEW is created and populated based upon the modifications to the metadata MD.01-MD.N. Subsequently, alternate operations are executed in step 21B.04.

In the alternative, when it is determined in step 21B.06 that no new record is necessary to categorize the information within the new digitized textual data, in step 21B.12 it is determined whether modification to a segment record SR.01-SR.N is needed to reflect the received new digitized textual data. When it is determined that revisions to a segment record SR.01-SR.N are needed to reflect the received new digitized textual data, the metadata MD.01-MD.N is first modified in step 21B.14, and the segment record SR.01-SR.N is subsequently modified to reflect the modification to the metadata MD.01-MD.N in step 21B.16. Alternately, when it is determined in step 21B.14 that no modification to a segment record SR.01-SR.N is necessary in response to the received new digitized textual data, in step 21B.18 it is determined whether modifications to a node record NR.01-NR.N are necessary in response to the received new digitized textual data. When it is determined in step 21B.18 that a node record NR.01-NR.N need be modified in response to the received new digitized textual data, the metadata MD.01-MD.N is updated in step 21B.20. Subsequently, in step 21B.22, the node record NR.01-NR.N is updated to reflect the modifications to the metadata MD.01-MD.N. Alternate operations are subsequently executed in step 21B.04. When, in the alternative, it is determined in step 21B.18 that no modification need be made to the node record ND.01-ND.N, the steps 21B.02 through 21B.22 are executed as deemed necessary by the human editor or by the editing system 200, enabled by the system software SW.5.

Referring now generally to the Figures, and particularly to FIG. 22A, FIG. 22A is a process chart of a further preferred embodiment of the invented method wherein a segment record SR.01-SR.N is populated by a human editor, and metadata MD.01-MD.N is subsequently revised by a human editor. The human editor proceeds from step 21A.06 of the method of FIG. 21A to step 22A.00 of FIG. 22A. In step 22A.00 the human editor assigns a segment record identifier SR.ID.01-SR.ID.N to the new segment record SR.NEW, by which the new segment record SR.NEW may be identified either to the human editor, or to the editing system 200. In step 22A.02 the human editor populates the new segment record SR.NEW with data derived from a digitized text. The information with which the human editor populates the new segment record SR.NEW may optionally be, but is not limited to, a plurality of tags T.01-T.N; a sequence number SEQ.001-SEQ.N wherein the new segment record SR.NEW has a unique segment number SEQ.001-SEQ.N that orders the segments according to a one-dimensional sequence; and a text segment SG.01-SG.N derived by the human editor from the source text 100. In step 22A.04 the human editor revises the metadata MD.01-MD.N to reflect the creation and population of the new segment record SR.NEW. The human editor subsequently proceeds to step 21A.04 of the method of FIG. 21A.

Referring now generally to the Figures, and particularly to FIG. 22B, FIG. 22B is a process chart of a yet further preferred embodiment of the invented method wherein metadata MD.01-MD.N is edited, and a new segment record SR.NEW is subsequently populated by a human editor. The human editor proceeds from step 21B.06 of the method of FIG. 21B to step 22B.00. In step 22B.00 the human editor assigns a segment record identifier SR.ID.01-SR.ID.N to the new segment record SR.NEW, by which the new segment record SR.NEW may be identified either to the human editor, or to the editing system 200. In step 22B.02 the human editor revises the metadata MD.01-MD.N. In step 22B.04 the human editor populates the new segment record SR.NEW with data derived from a digitized text. The information with which the human editor populates the new segment record SR.NEW may optionally be, but is not limited to, a plurality of tags T.01-T.N; a sequence number SEQ.001-SEQ.N wherein the new segment record SR.NEW has a unique segment number SEQ.001-SEQ.N that orders the segments according to a one-dimensional sequence; and a text segment SG.01-SG.N derived by the human editor from the source text 100. The human editor subsequently proceeds to step 21B.04 of the method of FIG. 21B.

Referring now generally to the Figures, and particularly to FIG. 22C, FIG. 22C is a process chart of a yet additional preferred embodiment of the invented method wherein a new segment record SR.NEW is populated by a human editor, and the metadata MD.01-MD.N is revised by the system software SW.5 enabling the editing system 200. The human editor proceeds from step 21A.06 of the method of FIG. 21A to step 22C.00 of FIG. 22C. In step 22C.00 the human editor assigns a segment record identifier SR.ID.01-SR.ID.N to the new segment record SR.NEW, by which the new segment record SR.NEW may be identified either to the human editor, or to the editing system 200. In step 22C.02 the human editor populates the new segment record SR.NEW with data derived from a digitized text. The information with which the human editor populates the new segment record SR.NEW may optionally be, but is not limited to, a plurality of tags T.01-T.N; a sequence number SEQ.001-SEQ.N wherein the new segment record SR.NEW has a unique segment number SEQ.001-SEQ.N that orders the segments according to a one-dimensional sequence; and a text segment SG.01-SG.N derived by the human editor from the source text 100. In step 22C.04 the system software SW.5 enables the editing system 200 to edit the metadata MD.01-MD.N to reflect the creation and population of the new segment record SR.NEW. The human editor subsequently proceeds to step 21A.04 of the method of FIG. 21A.

Referring now generally to the Figures, and particularly to FIG. 22D, FIG. 22D is a process chart of a yet additional preferred embodiment of the invented method wherein metadata MD.01-MD.N is revised by a human editor, and a new segment record SR.NEW is populated by the system software SW.5. The human editor proceeds from step 21B.06 of the method of FIG. 21D to step 22D.00. In step 22D.00 the human editor assigns a segment record identifier SR.ID.01-SR.ID.N to the new segment record SR.NEW, by which the new segment record SR.NEW may be identified either to the human editor, or to the editing system 200. In step 22D.02 the human editor revises the metadata MD.01-MD.N. In step 22D.04 the system software SW.5 directs the editing system 200 to populate the new segment record SR.NEW with data derived from a digitized text. The information with which the system software SW.5 populates the new segment record SR.NEW may optionally be, but is not limited to, a plurality of tags T.01-T.N; a sequence number SEQ.001-SEQ.N wherein the new segment record SR.NEW has a unique segment number SEQ.001-SEQ.N that orders the segments according to a one-dimensional sequence; and a text segment SG.01-SG.N derived by the human editor from the source text 100. The human editor subsequently proceeds to step 21B.04 of the method of FIG. 21B.

Referring now generally to the Figures, and particularly to FIG. 22E, FIG. 22E is a process chart of an additional preferred embodiment of the invented method wherein a new segment record SR.NEW is populated by the system software SW.5 enabling the editing system 100 and the metadata MD.01-MD.N is updated by the human editor. The system software SW.5 proceeds from step 21A.06 of the method of FIG. 21A to step 22E.00 of FIG. 22E. In step 22E.00 a segment record identifier SR.ID.01-SR.ID.N is assigned to the new segment record SR.NEW, by which the new segment record SR.NEW may be identified either to the human editor, or to the editing system 200. In step 22E.02 the system software SW.5 enables the editing system 200 to populate the new segment record SR.NEW with data derived from a digitized text. The information with which the system software SW.5 directs the editing system 200 to populate the new segment record SR.NEW may optionally be, but is not limited to, a plurality of tags T.01-T.N; a sequence number SEQ.001-SEQ.N wherein the new segment record SR.NEW has a unique segment number SEQ.001-SEQ.N that orders the segments according to a one-dimensional sequence; and a text segment SG.01-SG.N derived by the system software SW.5 from the source text 100. In step 22E.04 the human editor revises the metadata MD.01-MD.N to reflect the creation and population of the new segment record SR.NEW. The human editor subsequently proceeds to step 21A.04 of the method of FIG. 21A.

Referring now generally to the Figures, and particularly to FIG. 22F, FIG. 22F is a process chart of a further preferred embodiment of the invented method wherein metadata MD.01-MD.N is revised by the system software SW.5 and a new segment record SR.NEW is populated by the human editor. The human editor proceeds from step 21B.06 of the method of FIG. 21D to step 22F.00. In step 22F.00 the human editor assigns a segment record identifier SR.ID.01-SR.ID.N to the new segment record SR.NEW, by which the new segment record SR.NEW may be identified either to the human editor, or to the editing system 200. In step 22F.02 system software SW.5 directs the editing system 200 revises the metadata MD.01-MD.N. In step 22F.04 the human editor populates the new segment record SR.NEW with data derived from a digitized text. The information with which the human editor populates the new segment record SR.NEW may optionally be, but is not limited to, a plurality of tags T.01-T.N; a sequence number SEQ.001-SEQ.N wherein the new segment record SR.NEW has a unique segment number SEQ.001-SEQ.N that orders the segments according to a one-dimensional sequence; and a text segment SG.01-SG.N derived by the human editor from the source text 100. The human editor subsequently proceeds to step 21B.04 of the method of FIG. 21B.

Referring now generally to the Figures, and particularly to FIG. 23A, FIG. 23A is a process chart of a further preferred embodiment of the invented method wherein a new node record NR.NEW is populated by a human editor, and metadata MD.01-MD.N is revised by a human editor. The human editor proceeds from step 21A.06 of the method of FIG. 21A to step 23A.00 of FIG. 23A. In step 23A.00 the human editor assigns a node record identifier NR.ID.01-NR.ID.N to the new node record NR.NEW, by which the new node record NR.NEW may be identified either to the human editor, or to the editing system 200. In step 23A.02 the human editor populates the new node record NR.NEW with data derived from a digitized text. The information with which the human editor populates the new node record NR.NEW may optionally be, but is not limited to, a plurality of tag identifiers T.ID.01-T.ID.N; a plurality of alternate node record identifiers NR.ID.01-NR.01.N, and a plurality of segment record identifiers SR.ID.01-SR.ID.N; and one or more thread identifiers TH.ID.01-TH.ID.N, which narrative threads TH.01-TH.N with which the plurality of nodes ND.01-ND.N are associated. In step 23A.04 the human editor revises the metadata MD.01-MD.N to reflect the creation and population of the new node record NR.NEW. The human editor subsequently proceeds to step 21A.04 of the method of FIG. 21A.

Referring now generally to the Figures, and particularly to FIG. 23B, FIG. 23B is a process chart of a yet further preferred embodiment of the invented method wherein metadata MD.01-MD.N is modified by a human editor, and a new node record ND.NEW is subsequently populated by a human editor. The human editor proceeds from step 21B.06 of the method of FIG. 21B to step 23B.00 of FIG. 23B. In step 23B.00 the human editor assigns a node record identifier NR.ID.01-NR.ID.N to the new node record NR.NEW, by which the new node record NR.NEW may be identified either to the human editor, or to the editing system 200. In step 23B.02 the human editor revises the metadata MD.01-MD.N. In step 23B.04 the human editor populates the new node record NR.NEW with data derived from a digitized text. The information with which the human editor populates the new node record NR.NEW may optionally be, but is not limited to, a plurality of tag identifiers T.ID.01-T.ID.N; a plurality of alternate node record identifiers NR.ID.01-NR.01.N, and a plurality of segment record identifiers SR.ID.01-SR.ID.N; and one or more thread identifiers TH.ID.01-TH.ID.N, which narrative threads TH.01-TH.N with which the plurality of nodes ND.01-ND.N are associated. The human editor subsequently proceeds to step 21B.04 of the method of FIG. 21B.

Referring now generally to the Figures, and particularly to FIG. 23C, FIG. 23C is a process chart of a yet additional preferred embodiment of the invented method wherein a new node record ND.NEW is populated by a human editor, and the metadata MD.01-MD.N is revised by the software system SW.5 enabling the editing system 200. The human editor proceeds from step 21A.06 of the method of FIG. 21A to step 23C.00 of FIG. 23C. In step 23C.00 the human editor assigns a node record identifier NR.ID.01-NR.ID.N to the new node record NR.NEW, by which the new node record NR.NEW may be identified either to the human editor, or to the editing system 200. In step 23C.02 the human editor populates the new node record NR.NEW with data derived from a digitized text. The information with which the human editor populates the new node record NR.NEW may optionally be, but is not limited to, a plurality of tag identifiers T.ID.01-T.ID.N; a plurality of alternate node record identifiers NR.ID.01-NR.01.N, and a plurality of segment record identifiers SR.ID.01-SR.ID.N; and one or more thread identifiers TH.ID.01-TH.ID.N, which narrative threads TH.01-TH.N with which the plurality of nodes ND.01-ND.N are associated. In step 23C.04 the system software SW.5 directs the editing system 200 to revise the metadata MD.01-MD.N to reflect the creation and population of the new node record NR.NEW. The human editor subsequently proceeds to step 21A.04 of the method of FIG. 21A.

Referring now generally to the Figures, and particularly to FIG. 23D, FIG. 23D is a process chart of a yet additional preferred embodiment of the invented method wherein metadata MD.01-MD.N is revised by a human editor, and a new node record ND.NEW is populated by the editing system 200 as enabled by the system software SW.5. The human editor proceeds from step 21B.06 of the method of FIG. 21B to step 23D.00 of FIG. 23D. In step 23D.00 the human editor assigns a node record identifier NR.ID.01-NR.ID.N to the new node record NR.NEW, by which the new node record NR.NEW may be identified either to the human editor, or to the editing system 200. In step 23D.02 the human editor revises the metadata MD.01-MD.N. In step 23D.04 the system software SW.5 directs the editing system 200 to populate the new node record NR.NEW with data derived from a digitized text. The information with which the system software SW.5 directs the editing system 200 to populate the new node record NR.NEW may optionally be, but is not limited to, a plurality of tag identifiers TID.01-T.ID.N; a plurality of alternate node record identifiers NR.ID.01-NR.01.N, and a plurality of segment record identifiers SR.ID.01-SR.ID.N; and one or more thread identifiers TH.ID.01-TH.ID.N, which narrative threads TH.01-TH.N with which the plurality of nodes ND.01-ND.N are associated. The human editor subsequently proceeds to step 21B.04 of the method of FIG. 21B.

Referring now generally to the Figures, and particularly to FIG. 23E, FIG. 23E is a process chart of an additional preferred embodiment of the invented method wherein a new node record NR.NEW is populated by the editing system 200 as enabled by the system software SW.5 and the metadata MD.01-MD.N is revised by a human editor. The human editor proceeds from step 21A.06 of the method of FIG. 21A to step 23E.00 of FIG. 23E. In step 23E.00 the human editor assigns a node record identifier NR.ID.01-NR.ID.N to the new node record NR.NEW, by which the new node record NR.NEW may be identified either to the human editor, or to the editing system 200. In step 23E.02 the system software SW.5 enables the editing system 200 to populate the new node record NR.NEW with data derived from a digitized text. The information with which the system software SW.5 enables the editing system 200 to populate the new node record NR.NEW may optionally be, but is not limited to, a plurality of tag identifiers T.ID.01-T.ID.N; a plurality of alternate node record identifiers NR.ID.01-NR.01.N, and a plurality of segment record identifiers SR.ID.01-SR.ID.N; and one or more thread identifiers TH.ID.01-TH.ID.N, which narrative threads TH.01-TH.N with which the plurality of nodes ND.01-ND.N are associated. In step 23E.04 the human editor revises the metadata MD.01-MD.N to reflect the creation and population of the new node record NR.NEW. The human editor subsequently proceeds to step 21A.04 of the method of FIG. 21A.

Referring now generally to the Figures, and particularly to FIG. 23F, FIG. 23F is a process chart of a further preferred embodiment of the invented method wherein metadata MD.01-MD.N is revised by the editing system 200 as enabled by the system software SW.5 and a new node record NR.NEW is populated by the human editor. The human editor proceeds from step 21B.06 of the method of FIG. 21B to step 23F.00 of FIG. 23F. In step 23F.00 the human editor assigns a node record identifier NR.ID.01-NR.ID.N to the new node record NR.NEW, by which the new node record NR.NEW may be identified either to the human editor, or to the editing system 200. In step 23F.02 the system software SW.5 enables the editing system 200 to revise the metadata MD.01-MD.N. In step 23F.04 the human editor populates the new node record NR.NEW with data derived from a digitized text. The information with which the human editor populates the new node record NR.NEW may optionally be, but is not limited to, a plurality of tag identifiers T.ID.01-T.ID.N; a plurality of alternate node record identifiers NR.ID.01-NR.01.N, and a plurality of segment record identifiers SR.ID.01-SR.ID.N; and one or more thread identifiers TH.ID.01-TH.ID.N, which narrative threads TH.01-TH.N with which the plurality of nodes ND.01-ND.N are associated. The human editor subsequently proceeds to step 21B.04 of the method of FIG. 21B.

Referring now generally to the Figures, and particularly to FIG. 24A, FIG. 24A is a process chart of a further preferred embodiment of the invented method wherein a segment record SR.01-SR.N is revised by the human editor, and the metadata MD.01-MD.N is revised by the human editor. The human editor proceeds from step 21A.12 of the method of FIG. 21A to step 24A.00 of FIG. 24A. In step 24A.00 the human editor selects a segment record SR.01-SR.N for revision. In step 24A.02 the human editor revises one or all aspects of a segment record SR.01-SR.N, including but not limited to, the tags T.01-T.N, and/or the text segment SG.01-SG.N. Revision of the segment record SR.01-SR.N may optionally include deletion of the segment record SR.01-SR.N. In step 24A.04 the human editor revises the metadata MD.01-MD.N to reflect the alterations made to the selected segment record SR.01-SR.N. The human editor subsequently proceeds to step 21A.04 of the method of FIG. 21A.

Referring now generally to the Figures, and particularly to FIG. 24B, FIG. 24B is a process chart of a yet further preferred embodiment of the invented method wherein metadata MD.01-MD.N is modified by a human editor, and a segment record SR.01-SR.N is subsequently revised by the human editor. The human editor proceeds from step 21B.12 of the method of FIG. 21B to step 24B.00 of FIG. 24B. In step 24B.00 the human editor selects a segment record SR.01-SR.N for revision. In step 24B.02 the human editor revises the metadata MD.01-MD.N. In step 24B.04 the human editor revises one or all aspects of a segment record SR.01-SR.N, including but not limited to, the tags T.01-T.N, and/or the text segment SG.01-SG.N. Revision of the segment record SR.01-SR.N may optionally include deletion of the segment record SR.01-SR.N. The human editor subsequently proceeds to step 21B.04 of the method of FIG. 21B.

Referring now generally to the Figures, and particularly to FIG. 24C, FIG. 24C is a process chart of a yet additional preferred embodiment of the invented method wherein a segment record SR.01-SR.N is modified by a human editor, and the metadata MD.01-MD.N is revised by the editing system 200 as directed by the system software SW.5. The human editor proceeds from step 21A.12 of the method of FIG. 21A to step 24C.00 of FIG. 24C. In step 24C.00 the human editor selects a segment record SR.01-SR.N for revision. In step 24C.02 the human editor revises one or all aspects of a segment record SR.01-SR.N, including but not limited to, the tags T.01-T.N, and/or the text segment SG.01-SG.N. Revision of the segment record SR.01-SR.N may optionally include deletion of the segment record SR.01-SR.N. In step 24C.04 the system software SW.5 enables the editing system 200 to revise the metadata MD.01-MD.N to reflect the alterations made to the selected segment record SR.01-SR.N. The human editor subsequently proceeds to step 21A.04 of the method of FIG. 21A.

Referring now generally to the Figures, and particularly to FIG. 24D, FIG. 24D is a process chart of a yet additional preferred embodiment of the invented method wherein metadata MD.01-MD.N is revised by a human editor, and a segment record SG.01-SG.N is revised by the editing system 200 as enabled by the system software SW.5. The human editor proceeds from step 21B.12 of the method of FIG. 21B to step 24D.00 of FIG. 24D. In step 24D.00 the human editor selects a segment record SR.01-SR.N for revision. In step 24D.02 the human editor revises the metadata MD.01-MD.N. In step 24D.04 the system software SW.5 directs the editing system 200 to revise one or all aspects of a segment record SR.01-SR.N, including but not limited to, the tags T.01-T.N, and/or the text segment SG.01-SG.N. Revision of the segment record SR.01-SR.N may optionally include deletion of the segment record SR.01-SR.N. The human editor subsequently proceeds to step 21B.04 of the method of FIG. 21B.

Referring now generally to the Figures, and particularly to FIG. 24E, FIG. 24E is a process chart of an additional preferred embodiment of the invented method wherein a segment record SR.01-SR.N is modified by the editing system 200 as enabled by the system software SW.5 and the metadata MD.01-MD.N is revised by a human editor. The human editor proceeds from step 21A.12 of the method of FIG. 21A to step 24E.00 of FIG. 24E. In step 24E.00 the human editor selects a segment record SR.01-SR.N for revision. In step 24E.02 the system software SW.5 enables the editing system to revise one or all aspects of a segment record SR.01-SR.N, including but not limited to, the tags T.01-T.N, and/or the text segment SG.01-SG.N. Revision of the segment record SR.01-SR.N may optionally include deletion of the segment record SR.01-SR.N. In step 24E.04 the human editor revises the metadata MD.01-MD.N to reflect the alterations made to the selected segment record SR.01-SR.N. The human editor subsequently proceeds to step 21A.04 of the method of FIG. 21A.

Referring now generally to the Figure, and particularly to FIG. 24F, FIG. 24F is a process chart of a further preferred embodiment of the invented method wherein metadata MD.01-MD.N is revised by the editing system 200 as enabled by the system software SW.5 and a segment record SR.01-SR.N is modified by the human editor. The human editor proceeds from step 21B.12 of the method of FIG. 21B to step 24F.00 of FIG. 24F. In step 24F.00 the human editor selects a segment record SR.01-SR.N for revision. In step 24F.02 the system software SW.4 enables the editing system 200 to revise the metadata MD.01-MD.N. In step 24F.04 the human editor revises one or all aspects of a segment record SR.01-SR.N, including but not limited to, the tags T.01-T.N, and/or the text segment SG.01-SG.N. Revision of the segment record SR.01-SR.N may optionally include deletion of the segment record SR.01-SR.N. The human editor subsequently proceeds to step 21B.04 of the method of FIG. 21B.

Referring now generally to the Figures, and particularly to FIG. 25A, FIG. 25A is a process chart of a further preferred embodiment of the invented method wherein a node record NR.01-NR.N is revised by a human editor, and metadata MD.01-MD.N is revised by a human editor. The human editor proceeds from step 21A.18 of the method of FIG. 21A to step 25A.00 of FIG. 25A. In step 25A.00 the human editor selects a node record NR.01-NR.N. In step 25A.02 the human editor revises one or more aspects of the node record NR.01-NR.N, including, but not limited to a plurality of tag identifiers T.ID.01-T.ID.N; a plurality of alternate node record identifiers NR.ID.01-NR.01.N, and a plurality of segment record identifiers SR.ID.01-SR.ID.N; and/or one or more thread identifiers TH.ID.01-TH.ID.N. Revision of the node record NR.01-NR.N may optionally include deletion of the node record NR.01-NR.N. The human editor subsequently revises the metadata MD.01-MD.N in response to the revision to the node record NR.01-NR.N in step 25A.04. The human editor then proceeds to step 21A.04 of FIG. 21A.

Referring now generally to the Figures, and particularly to FIG. 25B, FIG. 25B is a process chart of a yet further preferred embodiment of the invented method wherein metadata MD.01-MD.N is modified by a human editor, and a node record NR.01-NR.N is subsequently revised by a human editor. The human editor proceeds from step 21B.18 of the method of FIG. 21B to step 25B.00 of FIG. 25B. In step 25B.00 the human editor selects a node record NR.01-NR.N. In step 25B.02 the human editor revises the metadata MD.01-MD.N. In step 25B.04 the human editor revises one or more aspects of the node record NR.01-NR.N, including, but not limited to a plurality of tag identifiers T.ID.01-T.ID.N; a plurality of alternate node record identifiers NR.ID.01-NR.01.N, and a plurality of segment record identifiers SR.ID.01-SR.ID.N; and/or one or more thread identifiers TH.ID.01-TH.ID.N in response to the modification of the metadata MD.01-MD.N. Revision of the node record NR.01-NR.N may optionally include deletion of the node record NR.01-NR.N. The human editor then proceeds to step 21A.04 of FIG. 21A.

Referring now generally to the Figures, and particularly to FIG. 25C, FIG. 25C is a process chart of a yet additional preferred embodiment of the invented method wherein a node record NR.01-NR.N is modified by a human editor, and the metadata MD.01-MD.N is revised by the editing system 200 as directed by the system software SW.5. The human editor proceeds from step 21A.18 of the method of FIG. 21A to step 25C.00 of FIG. 25C. In step 25C.00 the human editor selects a node record NR.01-NR.N. In step 25C.02 the human editor revises one or more aspects of the node record NR.01-NR.N, including, but not limited to a plurality of tag identifiers T.ID.01-T.ID.N; a plurality of alternate node record identifiers NR.ID.01-NR.01.N, and a plurality of segment record identifiers SR.ID.01-SR.ID.N; and/or one or more thread identifiers TH.ID.01-TH.ID.N. Revision of the node record NR.01-NR.N may optionally include deletion of the node record NR.01-NR.N. The system software SW.5 directs the editing system to modify the metadata MD.01-MD.N in response to the revision to the node record NR.01-NR.N in step 25C.04. The human editor then proceeds to step 21A.04 of FIG. 21A.

Referring now generally to the Figures, and particularly to FIG. 25D, FIG. 25D is a process chart of a yet additional preferred embodiment of the invented method wherein metadata MD.01-MD.N is revised by a human editor, and a node record NR.01-NR.N is revised by the editing system 200 as directed by the system software SW.5. The human editor proceeds from step 21B.18 of the method of FIG. 21B to step 25D.00 of FIG. 25D. In step 25D.00 the human editor selects a node record NR.01-NR.N. In step 25D.02 the human editor revises the metadata MD.01-MD.N. In step 25D.04 the system software SW.5 directs the editing system 200 to modify one or more aspects of the node record NR.01-NR.N, including, but not limited to a plurality of tag identifiers T.ID.01-T.ID.N; a plurality of alternate node record identifiers NR.ID.01-NR.01.N, and a plurality of segment record identifiers SR.ID.01-SR.ID.N; and/or one or more thread identifiers TH.ID.01-TH.ID.N in response to the modification of the metadata MD.01-MD.N. Revision of the node record NR.01-NR.N may optionally include deletion of the node record NR.01-NR.N. The human editor then proceeds to step 21A.04 of FIG. 21A.

Referring now generally to the Figures, and particularly to FIG. 25E, FIG. 25E is a process chart of an additional preferred embodiment of the invented method wherein a node record NR.01-NR.N is modified by the editing system 200 as directed by the system software SW.5 and the metadata MD.01-MD.N is revised by a human editor. The human editor proceeds from step 21A.18 of the method of FIG. 21A to step 25E.00 of FIG. 25E. In step 25E.00 the human editor selects a node record NR.01-NR.N. In step 25E.02 the system software SW.5 directs the editing system 200 to revise one or more aspects of the node record NR.01-NR.N, including, but not limited to a plurality of tag identifiers T.ID.01-T.ID.N; a plurality of alternate node record identifiers NR.ID.01-NR.01.N, and a plurality of segment record identifiers SR.ID.01-SR.ID.N; and/or one or more thread identifiers TH.ID.01-TH.ID.N. Revision of the node record NR.01-NR.N may optionally include deletion of the node record NR.01-NR.N. The human editor modifies the metadata MD.01-MD.N in response to the revision to the node record NR.01-NR.N in step 25E.04. The human editor then proceeds to step 21A.04 of FIG. 21A.

Referring now generally to the Figures, and particularly to FIG. 25F, FIG. 25F is a process chart of a further preferred embodiment of the invented method wherein metadata MD.01-MD.N is revised by the editing system 200 as directed by the system software SW.5 and a node record NR.01-NR.N is modified by the human editor. The human editor proceeds from step 21B.18 of the method of FIG. 21B to step 25F.00 of FIG. 25F. In step 25F.00 the human editor selects a node record NR.01-NR.N. In step 25F.02 the system software SW.5 directs the editing system 200 to modify the metadata MD.01-MD.N. In step 25F.04 the human editor revises one or more aspects of the node record NR.01-NR.N, including, but not limited to a plurality of tag identifiers T.ID.01-T.ID.N; a plurality of alternate node record identifiers NR.ID.01-NR.01.N, and a plurality of segment record identifiers SR.ID.01-SR.ID.N; and/or one or more thread identifiers TH.ID.01-TH.ID.N in response to the modification of the metadata MD.01-MD.N. Revision of the node record NR.01-NR.N may optionally include deletion of the node record NR.01-NR.N. The human editor then proceeds to step 21A.04 of FIG. 21A.

Referring now generally to the Figures FIG. 26 is a block diagram of the ebook 2, including a plurality of exemplary segment records SR.01-SR.N, a plurality of exemplary node records NR.01-NR.N, exemplary metadata MD.01, the table 1700, and the second GUI software SW.7.

Referring now generally to the Figures, and particularly to FIG. 27A, FIG. 27A is a block diagram of exemplary metadata MD.01. The exemplary metadata MD.01 comprises a plurality of node record identifiers NR.ID.01-NR.ID.N, by which nodes ND.01-ND.N associated with text segments SG.001-SG.N and/or tags T.01-T.N may be identified within the system or by the human editor; a plurality of exemplary segment record identifiers SR.ID.01, SR.ID.57, SR.ID.572, and SR.ID.N; and a plurality of exemplary tags T.01, T.BILL, T.PARK, T.38, T.LAKE, T.DEF, T.823, and T.N.

Referring now generally to the Figures, and particularly to FIG. 27B, FIG. 27B is a block diagram is exemplary revised metadata MD.01.REV, wherein the exemplary revised metadata MD.01.REV has been modified in response to revision to the text segments SG.001-SG.N and/or the tags T.01-T.N by the human editor. The modifications to the metadata MD.01 may optionally be executed by the system, or by the human editor, and subsequently be recorded by the editing system. The revised metadata MD.01 comprises a plurality of node record identifiers NDID.01-ND.ID.N, a plurality of exemplary modified text segment identifiers SR.ID.56, SR.ID.73, SR.ID.920, and SR.ID.N; and a plurality of modified tags T.01, T.LIZ, T.HOUSE, T.87, T.SHOP, T.370, and T.N.

FIGS. 28A-28D are block diagrams of exemplary node records NR.01-NR.N. Each exemplary node record NR.01-NR.N comprises a node record identifier NR.ID.01-NR.ID.N, by which the node record NR.01-NR.N may be identified; pointers to alternate node records NR.01-NR.N, whereby the node records NR.01-NR.N may be indicated as part of a series of nodes ND.01-ND.N; a node ND.01-ND.N; one or more thread identifiers TH.ID.01-TH.ID.N, by which narrative threads which the nodes ND.01-ND.N indicate may be identified by the system or by the human editor; and a plurality of tag identifiers T.ID.01-T.ID.N, and T.ID.BILL, T.ID.WOOD, T.ID.LARA, and T.ID.WIFE.

One skilled in the art will recognize that the foregoing examples are not to be taken in a limiting sense and are simply illustrative of at least some of the aspects of the present invention. 

What is claimed is:
 1. A method comprising: entering a source digitized text into a memory of an information technology system; delineating the source by an editor into a plurality of segments (“segments”); associating by an editor each segment of the segments with at least one navigation tag of a plurality of navigation tags; separately associating by an editor each node of a plurality nodes with at least one segment of the segments; and generating a metadata, the metadata specifying at least one segment of the segments and at least one association of at least one navigation tags of the plurality of navigation tags with the at least one segment.
 2. The method of claim 1, wherein generating the metadata further comprises specifying in the metadata a first plurality of the segments and associations of navigation tags of the plurality of navigation tags with at least one segment.
 3. The method of claim 2, wherein generating the metadata further comprises specifying in the metadata a plurality of associations of the navigation tags of the plurality of navigation tags with the first plurality of the segments.
 4. The method of claim 1, wherein generating the metadata further comprises specifying in the metadata at least one node of the plurality nodes.
 5. The method of claim 4, wherein generating the metadata further comprises specifying in the metadata at least one association of at least one navigation tag of the plurality of navigation tags with the at least one node.
 6. The method of claim 4, wherein generating the metadata further comprises specifying in the metadata a first plurality of the segments and associations of navigation tags of the plurality of navigation tags with the at least one segment.
 7. The method of claim 6, wherein generating the metadata further comprises specifying in the metadata a plurality of associations of the navigation tags of the plurality of navigation tags with the first plurality of the segments.
 8. The method of claim 1, further comprising: providing a digitized information (“new segment”) to the information technology system; associating the new segment by the editor with at least one navigation tag of the plurality of navigation tags (“assigned tag”); and revising the metadata to specify the new segment and the assigned tag.
 9. The method of claim 8, further comprising revising the metadata to indicate the association of the new segment with the assigned tag.
 10. The method of claim 9, further comprising revising the metadata to specify an additional association of the new segment with a second navigation tag of the plurality of navigation tags.
 11. The method of claim 8, further comprising the editor revising the metadata to associate at least one node of the plurality nodes with the new segment.
 12. The method of claim 11, further comprising the editor revising the metadata to associate a second one node of the plurality nodes with the new segment.
 13. The method of claim 8, wherein the new segment includes text data.
 14. The method of claim 8, wherein the new segment includes visual image data.
 15. The method of claim 8, wherein the new segment includes audio data.
 16. The method of claim 1, further comprising: selecting a segment (“revised segment”) of the segments; and revising the metadata to newly specify an association of the revised segment and at least one navigation tag of the plurality of navigation tags.
 17. The method of claim 16, wherein the editor specifies at least one navigation tag for association with the revised segment.
 18. The method of claim 1, further comprising: the editor designating a new navigation tag (“new tag”); selecting a segment (“selected segment”) of the segments; and revising the metadata to newly specify an association of the selected segment with the new tag.
 19. The method of claim 1, further comprising: the editor designating a new node (“new node”); selecting a segment (“selected segment”) of the segments; and revising the metadata to newly specify an association of the selected segment with the new node.
 20. The method of claim 19, further comprising: the editor designating a new navigation tag (“new tag”); and revising the metadata to newly specify an association of the selected segment with the new tag. 